Cream of the Crop 12

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 12 / Cream of the Crop 12 (Part II) / Cream of the Crop 12 (Part II).iso / OS2 / FM121WB.ZIP / FMOVE.DOC < prev next >

Wrap

Text File | 1996-02-08 | 13.6 KB | 296 lines

FMove 1.2 - Copyright 1993, 1996, Mike Walker. All rights reserverd. ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ Introduction ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ Fmove is a utility used to move or kill files. Files may be killed or moved based on number of days old or size. This utility came about because I just got tired of looking for such a utility myself. This is a protect mode dos app and needs rtm.exe in order to run. I have included rtm inside the archive. ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ License and registration ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ This program is Shareware. You may use this beta free of charge. The license to use this beta version will expire upon the release of the next version of Fmove. The release version will be distributed as low cost shareware or freeware, I have not decided yet. :-) If the release version of Fmove is released as low cost shareware a registration fee will be required for a license to use Fmove. Either way I will be willing to accept any donations in appreciation for this work. You may not charge anything for this program other than a nominal fee for the transfer of the program to the transfer media and the cost of that media. You may distribute this program freely as long as this document and all files contained in the original archive remain in thier original state. The author reserves the right to change this license argreement. THE PROGRAM IS PROVIDED "AS-IS". NO WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, ARE MADE AS TO IT OR ANY MEDIUM IT MAY BE ON. NO REMEDY IS PROVIDED BY THE AUTHOR FOR INDIRECT, CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES ARISING FROM IT, INCLUDING SUCH FROM NEGLIGENCE, STRICT LIABILITY, OR BREACH OF WARRANTY OR CONTRACT, EVEN AFTER NOTICE OF THE POSSIBILITY OF SUCH DAMAGES. USE AT YOUR OWN RISK. ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ Installation ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ Extract the archive to your utilities directory, or somewhere specifed in the path. Once extracted you will need to create a config file, or edit the sample configuration suppied. If you have registered or have and evaluation version of fmove place your key file in the same directory as fmove.exe. The key file must be named fmove.key since this is name that fmove will look for. Evaluation keys will expire and the expiry date will be displayed when you run fmove. ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ Command Line Options ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ -c Used to specify the config file to use. -s Used to specify the schedule to run. (See schedules latter in this doc). eg. Fmove -csample.cfg -sdostuff ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ The Config File ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ The config file can be any name that you choose. When you run the program you will need to specify the name on the command line using the -c command line switch. If you do not specify a config file name an attempt to read the default fmove.cfg will be made. All commands within the should all start in the first column of a line. Any line starting with a semi-colon will be considered to be a comment. Do not place comments at the end of command lines.The commands are divided into two groups, global commands and action verbs. There is a maximum of 255 action verbs that can be defined in the config file. If this is not sufficient then you can use multiple config files or schedules. Also keep in mind that the action verbs are preformed in the order that they appear in the config file. One last note, do not use trailing backslashes for any of the paths defined for the action verbs. ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ Global Commands ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ UserName Syntax: UserName Your_Registered_Name If you have a registration key you need to define the name that you used when registering, and use the key that was provided to you with the RegKey command. If you are using an evaluation version or beta of this program do not define a user name. Note: Underscores must be used in place of spaces in your name for the UserName command. ArcFile Syntax: ArcFile FullPath The ArcFile command is used for archiving descriptions of killed files. The file name that you use here is appended to when files are killed. Descriptions will also be moved to this file when Remiss is used. LogFile Syntax: LogFile FullPath The Logfile command is used for logging program activity. The log that is created is a binkley style log. BBS Syntax: [MAX3]|[FILESBBS] Currently there are two possible values for this command. Max3 tells fmove to read maximus file areas by area name. FilesBBS tells fmove to use full path names to the file areas. This command ditates how the move and kill commands area used. if the max3 mode is enabled using this command areas will be searched by area name. With max3 mode you will have to replace all paths names with the appropriate area name. BBSPath Syntax: BBSPath FullPath Full path to the BBS system files. Only required for the Max3 support. Do not specify any file names here just the path to the BBS system files eg. D:\MAX ReIndex Syntax: ReIndex FullPath This is the path to your file database build utility. eg. D:\MAX\FB.EXE ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ Action Verbs ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ Move Syntax: Move [@]SourcePath TargetPath [-dDays] [-sMaxSize] [-kKeepDays] This verb is used to move files from one area to another. The days portion of this command is optional. If you do not specify a number of days with the -d switch the number of days in the global section will be used. If the global command days was not used and the number of days was not specified for the move command, then all files in the source dir will be moved. The number of days for the move command will always take precidence over the global number of days. The -sMaxSize switch is used to specify the maximum size of a file in bytes. If a file exceeds maxsize then it will be moved regardless of the number of days specified. The -kKeepDays switch is used to specify the number of days to keep files when they exceed maxsize. Using this switch will cause files that are oversize to be kept for the number of days defined with the keep days switch. When moving files the descriptions in files.bbs are moved to the files.bbs at the target path. The @ character is used to insert the source path at the beginning of the description in the target files.bbs. Kill Syntax: Kill SourcePath [-dDays] [-sMaxSize] [-kKeepDays] The kill verb works the same way as the move verb. Except that instead of moving files they are killed. The only difference in syntax is that you do not specify a target path. Be careful with this one, if used incorrectly you could end up killing files that you wanted to keep. See documentation on the move command for explanation of the switches. ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ Misc Commands ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ All of these commands may be used either as global commands or within schedule blocks. Days Syntax: Days 30 This command is used to specify the default number of days used by the action verbs. This command is optional. KeepOrg Syntax: KeepOrg (Defaults to off) KeepOrg is used to keep the original description when moving or killing files. When this is used the description will not be removed from the source files.bbs file. Remiss Syntax: Remiss (Defaults to off) The remiss command is used to check for missing files when moving or killing files. If you use Remiss descriptions will be removed from files.bbs if the associated file is missing from the source directory. If you specify the ArcFile command then the descriptions will be placed in the ArcFile before removing them. Exclude Syntax: Exclude Mask The Exclude verb is used to exclude files from the move and kill commands. The mask follows the normal dos conventions. For more information on file masks see your dos manual. An example of this could be the following: Exclude PK*.* Exclude *.SDN This would cause Fmove not to move or kill any files that matched the file masks above. ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ Schedules ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ Schedules are now supported with Fmove. A schedule is simply a series of commands that are executed when the schedule is invoked. To define a schedule there are two config verbs. (Schedule, and EndSchedule). These two commands work as a pair to name and end schedules. Any commands appearing in the config file before the first schedule will be considered global commands. Global commands are executed for all schedules. To envoke a schedule there is a new command line option -s. When starting Fmove use the command line: Fmove -cfmove.cfg -sSchedule Where Schedule is the name of the schedule that you want to run. Schedule Syntax: Schedule [ScheduleName] This command starts the schedule. ScheduleName can be upto 32 characters in length. Any commands following the shedule command and before the next 'EndSchedule' will be considered part of that schedule. EndSchedule Syntax: EndSchedule The EndSchedule command does not take any parameters, it simply ends the current schedule. ┌──────────────────────────────────────────────────────────────────┐ │▒▒▒▒ How to contact me ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ └──────────────────────────────────────────────────────────────────┘ I can be reached at any of the addresss below. Please report any bugs that you find. If I don't know about the problem chances are it will not be fixed. FidoNet: 1:153/809.0 SigNet: 25:9604/110 Internet: mike_walker@mindlink.bc.ca BBS: Arcadia BBS - 28.8 VFC New Westminster, BC Canada (604) 526-5152 Note: If you are calling the BBS long distance and are using a USR modem be wary. I do have the occasional problem with dropping carriers upon receiving an inbound call from certain models of USR modems. Since this is a problem I would not leave the file request unattended.